Make the *_block_use
power types consistent with the *_entity_use
power types
#231
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR changes the implementation of the
*_block_use
power types to be consistent with the behavior of the*_entity_use
power types. It seems that this was already partially implemented (only on the client-side), so I decided to complete the implementation with this PR.This also changes the behavior of
edible_item
power type slightly, where the items that can be used on blocks are no longer prevented from being used. To accommodate for such use-cases (and some QoL stuff), this PR adds these new fields to the*_block_use
power types:Note
Powers with a priority value of equal or greater than 1 will be executed and will override the result of the interaction while powers with a priority value of equal or less than -1 will only be executed if the interaction results in a pass.
Powers with a priority value of 0 will be executed alongside the interaction and will not override the end result.
usage_phases
["block", "item"]
A block usage phase is a string that determines the phase when interacting with a block.
Note
The listed values are ordered by priority, with
"block"
being first and"item"
being last."block"
"item"